Transaction tool management intergration with change management

ABSTRACT

A change management system is integrated with a transaction tool management system including a processor for scheduling a change in status of at least one transaction tool of the transaction tool management system. The system includes a receiver that receives a request for approval of the change in the status of the at least one transaction tool, a storage that stores the received request, a transaction tool classification process module that classifies transaction tools, and a change management module that schedules the change in status when the request for approval is approved. The change management module uses classification information from the transaction tool classification process module to schedule the change in status. The change management system uses information available from the transaction tool management system to schedule the change in the status of the at least one transaction tool managed by the transaction tool management system.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of pending U.S. patent applicationSer. No. 12/640,060 filed on Dec. 17, 2009, which is a continuation ofU.S. patent application Ser. No. 10/975,335, filed Oct. 29, 2004, nowU.S. Pat. No. 7,661,110, issued on Feb. 9, 2010, the contents of whichare expressly incorporated by reference in their entireties.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to transaction tool management. Moreparticularly, the present invention relates to integrating changemanagement with transaction tool management for transaction tools usedin a communications network.

2. Background Information

Transaction tools are instruments issued by a third party to facilitatetransactions by “vouching” for a holder's identity and/ortrustworthiness. Accordingly, transaction tools are used to authenticatethe identity or trustworthiness of a bearer. Transaction tools areincreasingly being managed for issuers and recipients by managementsystems. As an example, for an issuer of credit cards, a managementsystem may facilitate day-to-day transactions by verifying creditavailability. Additionally, for an issuer of digital certificates, amanagement system may facilitate day-to-day transactions byauthenticating the validity of a digital certificate. Furthermore, froma recipient standpoint, a corporation may use a management system tomanage digital certificates installed by employees on computers in thecorporation's network. However, while the transaction tool managementsystems are available for transaction tools, the transaction toolmanagement systems do not provide change management functionality formanaging lifecycle events for transaction tools.

Change management is a term for the management of lifecycle events forhardware and software installed in a network. Alternatively, changemanagement may be identified as component resource management or anyother management system that provides the functionality of the changemanagement systems described herein. As an example, Vantive System 8.0.2from Vantive Corporation of Santa Clara, Calif., can be customized togenerate problem reports and request lifecycle changes to hardware andsoftware used in a local computer network. Other software used forchange management includes ProblemTracker from NetResults Corporation ofPalo Alto, Va. In a typical change management system, each requestedchange requires manual input and human interaction, which may be anextraordinary burden in a large network with numerous pieces of hardwareand software. For example, the Vantive system records changes and, whereappropriate, generates requests for approval of changes which requirethe approval of particular managers. The approvals are required because,in some circumstances, the requested change will, e.g., incur costs orrequire that a component of the local computer network be taken out ofservice.

Change management systems, if provided at all, are provided separatelyfrom the transaction tool management systems. Further, even if a changemanagement system is provided, it is not integrated with a transactiontool management system. As an example, the installation of an X.509digital certificate on a server may only be recorded in a changemanagement system if the server needs to be restarted as part of theprocess. However, another lifecycle event involving a transaction toolmay not be recorded in the change management system. The result is thatlifecycle events and changes which could be addressed automaticallyusing an integrated system are instead individually managed on acase-by-case basis using only a change management system.

When such lifecycle events for transaction tools are not coordinated(i.e., managed), the ability of a corporation to ensure the availabilityof a network is jeopardized. However, a change control coordinator isnot even always aware of such lifecycle events when a network includesnumerous hardware and software components and entries for changes arerecorded manually. Accordingly, a need exists to integrate changemanagement into transaction tool management, so that appropriatenotifications can be automatically made using the information andfunctionality of a transaction tool management system.

As an example, when a recipient renews an X.509 certificate on acomputer (e.g., a server or personal computer) in a local network, thecomputer may require restarting/rebooting. Therefore, a request for sucha change is logged in a change management system such as Vantive, andnotifications are sent to managers so that approvals can be obtained.Generating and processing such requests for a network with numerouscomputers is inefficient, particularly when a transaction toolmanagement system is already aware of an impending expiration for thedigital certificate to be renewed such that a request to renew a digitalcertificate could be generated automatically. Accordingly, if theinformation available to a transaction tool management system were to beprovided to a change management system, resources could be used moreefficiently. In particular, integrating transaction tool management andchange management will reduce the need for human interaction inimplementing lifecycle changes. Accordingly, a need exists forintegration of transaction tool management with change management.

To solve the above-described problems, a system is provided fortransaction tool management integration with change management.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is further described in the detailed descriptionthat follows, by reference to the noted drawings by way of non-limitingexamples of embodiments of the present invention, in which likereference numerals represent similar parts throughout several views ofthe drawing, and in which:

FIG. 1 shows an exemplary communications network architecture fortransaction tool management integration with change management,according to an aspect of the present invention;

FIG. 2 shows another exemplary communications network architecture fortransaction tool management integration with change management,according to an aspect of the present invention;

FIG. 3 shows another exemplary communications network architecture fortransaction tool management integration with change management,according to an aspect of the present invention;

FIG. 4 shows an exemplary change management apparatus for transactiontool management integration with change management, according to anaspect of the present invention; and

FIG. 5 is a flow diagram showing a method of transaction tool managementintegration with change management, according to an aspect of thepresent invention.

DETAILED DESCRIPTION OF THE INVENTION

In view of the foregoing, the present invention, through one or more ofits various aspects, embodiments and/or specific features orsub-components, is thus intended to bring out one or more of theadvantages as specifically noted below.

According to an aspect of the present invention, a change managementsystem coordinates information of a transaction tool managed by atransaction tool management system. The system includes a receiver thatreceives, over a communications network, activity information and/orlifecycle event information for the transaction tool. The system alsoincludes a storage that stores the received information. The systemfurther includes a processor that manages a change in a status of thetransaction tool based on the received information.

According to another aspect of the present invention, the changemanagement system includes a notifier that generates a perceptiblenotification for an impending change in the status of the transactiontool.

According to yet another aspect of the present invention, the receivedinformation is received from a manager that manages the transaction toolfor an issuer of the transaction tool.

According to still another aspect of the present invention, the receiverreceives requests for approval of changes to the status of thetransaction tool. The requests for approval are received by the changemanagement system from a client device that forwards the requests to thechange management system. The change management system determineswhether to approve the requested changes and notifies the client deviceof the determination.

According to another aspect of the present invention, the change in thestatus includes renewing an expiring transaction tool.

According to yet another aspect of the present invention, the receivedinformation includes information related to an upgrade to thetransaction tool.

According to still another aspect of the present invention, the receivedinformation is received in response to a status inquiry by the changemanagement system.

According to an aspect of the present invention, a method is providedfor coordinating information of a transaction tool managed by atransaction tool management system. The method includes receiving, overa communications network, activity information and/or lifecycle eventinformation for the transaction tool. The method also includes storingthe received information. The method further includes managing a changein a status of the transaction tool based on the received information.

According to another aspect of the present invention, the methodincludes generating a perceptible notification for an impending changein the status of the transaction tool.

According to yet another aspect of the present invention, the receivedinformation is received from a manager that manages the transaction toolfor an issuer of the transaction tool.

According to still another aspect of the present invention, the methodincludes receiving requests for approval of changes to the status of thetransaction tool. The requests for approval are received by the changemanagement system from a client device that forwards the requests to thechange management system. The method also includes determining whetherto approve the requested changes and notifying the client device of thedetermination.

According to another aspect of the present invention, the change in thestatus includes renewing an expiring transaction tool.

According to yet another aspect of the present invention, the lifecyclemanagement information includes information related to an upgrade of thetransaction tool.

According to still another aspect of the present invention, thelifecycle management information is received in response to a statusinquiry by a change management system.

According to an aspect of the present invention a computer readablemedium stores a program that coordinates information of a transactiontool managed by a transaction tool management system. The computerreadable medium includes a receiving code segment that receives, over acommunications network, activity information and/or lifecycle eventinformation for the transaction tool. The computer readable medium alsoincludes a storing code segment that stores the received information.The computer readable medium further includes a managing code segmentthat manages a change in a status of the at least one transaction toolbased on the received information.

According to another aspect of the present invention, the computerreadable medium includes a notifying code segment that generates aperceptible notification for an impending change in the status of the atleast one transaction tool.

According to yet another aspect of the present invention, the receivingcode segment receives information from a manager that manages thetransaction tool for an issuer of the transaction tool.

According to still another aspect of the present invention, thereceiving code segment receives requests for approval of changes to thestatus of the transaction tool that are automatically forwarded by aclient device to a change management system. The change managementsystem determines whether to approve the requested changes and notifiesthe client device of the determination.

According to another aspect of the present invention, the change in thestatus includes renewing an expiring transaction tool.

According to yet another aspect of the present invention, the receivedinformation includes information related to an upgrade to a transactiontool.

According to still another aspect of the present invention, the receivedinformation is received in response to a status inquiry by a changemanagement system.

A communications system is provided for transaction tool managementintegration with change management. The communications system includes achange management system that manages activity information and/orlifecycle event information for a transaction tool issued to a recipientby an issuer.

FIG. 1 shows an exemplary communications network architecture fortransaction tool management integration with change management. Asshown, a transaction tool management system 120 and a transaction toolmanagement system 130 are each connected to a change management system140 as well as an authentication system 160. An exemplary communicationsnetwork architecture that includes a transaction tool management systemand an authentication system is disclosed in U.S. patent applicationSer. No. 10/917,415 to NOVACK et al., filed Aug. 13, 2004 and entitled,“Pluggable Authentication for Transaction Tool Management Services”, thedisclosure of which is incorporated by reference herein in its entirety.

The transaction tool management system 120 includes a transaction toolserver 128. The transaction tool management system 130 also includes atransaction tool server 138. The transaction tool servers 128, 138 maybe used by, e.g., a corporation, to provide services as an issuer or asa recipient of transaction tools. When the transaction tool servers 128,138 are used by an issuer of transaction tools, the transaction toolservers 128, 138 are used to manage transaction tools for customers andclients. When the transaction tool servers 128, 138 are used by arecipient of transaction tools, the transaction tool servers 128, 138are used to manage transaction tools for the recipient's employees.

As an example, a telecommunications service provider may provide anetwork of servers and other computers for internal use, to managecomponents of the telecommunications network and to allow subscribers tochange services. The individual servers and other computers are providedwith X.509-compliant digital certificates for use in authenticatingcommunications with subscribers, customers and employees. Thetransaction tool servers 128, 138 manage the transaction tools installedon the network servers for internal use, to manage components of thetelecommunications network and to allow subscribers to change services.

In the example where the transaction tool management systems 120, 130manage transaction tools for a recipient of transaction tools, thechange management system 140 manages lifecycle events which involve thetransaction tools managed by the transaction tool management systems120, 130. The management of lifecycle events may include initiating theevents, analyzing the events, organizing information related to theevents, authorizing the events or merely recording the events. Lifecycleevents may include ordering a transaction tool, receiving a transactiontool, installing a transaction tool, activating a transaction tool,using a transaction tool, upgrading or “patching” a transaction tool,extracting a transaction tool, returning a transaction tool, deleting orcanceling a transaction tool, revoking a transaction tool, renewing atransaction tool, or changing any user information or term of use forthe transaction tool.

When the transaction tool servers 128, 138 are used by a recipient oftransaction tools, the transaction tool servers 128, 138 recordinformation for each transaction tool being managed. The information mayinclude an issuer of each transaction tool, a validity period for eachtransaction tool, and a computer in the network on which the transactiontool is installed.

An exemplary digital certificate complies with ITU-T RecommendationX.509. A digital certificate is issued by a certification authority andis installed for a networked computer such as the transaction toolservers 128, 138. The digital certificate is part of a public keyinfrastructure (PKI) that uses digital signatures to enhance thesecurity and authenticity of communications between computers in anetwork. When lifecycle events are impending or when lifecycle changesare requested for the digital certificates managed by the transactiontool management systems 120, 130, the transaction tool managementsystems 120, 130 forward the lifecycle event information to the changemanagement system 140. Accordingly, the change management system 140manages the lifecycle events for the transaction tools managed by thetransaction tool management systems 120, 130.

The transaction tool management systems 120, 130 may be provided by anissuer of transaction tools to manage the issued transaction tools. Forexample, a credit card company that issues credit cards may usetransaction tool management systems 120, 130 to manage activity for theissued credit cards. As the credit cards themselves are the transactiontools, the transaction tool management systems 120, 130 manage creditcards that are issued to individuals and which are not necessarilyassociated with any particular computer.

When the transaction tool management systems 120, 130 manage transactiontools for an issuer of transaction tools, the change management system140 manages activity and lifecycle events for the transaction tools.Accordingly, when lifecycle changes are requested for an issuedtransaction tool, the transaction tool management system 120, 130interacts with the change management system 140 to manage the lifecycleevents. For example, requests for an increase in a credit limit orrequests to cancel or replace a credit card may be referred to thechange management system 140 to obtain approvals or to record anyrequested changes.

The authentication system 160 can be used to authenticate communicationsbetween the transaction tool management systems 120, 130 and customers,subscribers and employees who communicate with the transaction toolmanagement systems 120, 130. As an example, transaction requests from acustomer may be forwarded to a third-party authentication system 160 toverify the customer's identity using information and/or data provided bythe customer.

The change management system 140 manages lifecycle event information fortransaction tools issued to or managed by the transaction toolmanagement systems 120, 130. For example, the change management system140 may store the date that a transaction tool will expire, and ensurethat a replacement transaction tool is made available before theexpiration of the original transaction tool. As another example, whenthe transaction tool servers 128, 138 are provided for a recipient oftransaction tools, the transaction tool management systems 120, 130 maydetermine that a particular issuer of, e.g., digital certificates, hasbeen compromised such that digital certificates issued by the issuer arenot trustworthy. Accordingly, the change management system 140 may becontacted to schedule immediate replacements for all digitalcertificates, installed on the local network, that were issued by theuntrustworthy issuer.

The change management system 140 includes a server 148 and a database149. The server 148 communicates directly with the transaction toolservers 128, 138. Further, the server 148 processes information receivedfrom the transaction tool servers 128, 138 and determines whether tomerely record the information or whether the information is a requestfor approval for a change requested for the transaction tools managed bythe transaction tool servers 128, 138. Lifecycle event information forthe transaction tools, including information for requested changes thatwere not ultimately authorized, is stored in the database 149 by theserver 148.

Accordingly, the change management system 140 is integrated with thetransaction tool management systems 120, 130, and efficiently uses theinformation available from the transaction tool management systems 120,130 to manage lifecycle events for the transaction tools managed by thetransaction tool management systems 130, 140. The change managementsystem 140 may manage lifecycle events in response to requests forlifecycle changes from customers, clients or employees, or in responseto periodic or targeted queries to the transaction tool managementsystems 120, 130 to obtain information regarding the transaction toolsbeing managed.

FIG. 2 shows another exemplary communications network architecture fortransaction tool management integration with change management. In theembodiment shown in FIG. 2, personal computer communications devices 201and 202 are managed by an integrated change management/transaction toolmanagement system 240. The change management/transaction tool managementsystem 240 includes a server 248 and a database 249.

As an example, the personal computer communications devices 201, 202 areeach provided with a transaction tool, such as an X.509 compliantdigital certificate that is managed by the change management/transactiontool management system 240. Accordingly, the changemanagement/transaction tool management system 240 manages activities andlifecycle events for the digital certificates provided to the personalcomputers 201, 202.

When lifecycle events are requested for the personal computers 201, 202for the transaction tools, the change management/transaction toolmanagement system 240 determines whether to authorize the requestedlifecycle events. For example, the change management/transaction toolmanagement system 240 may determine whether to authorize installation ofa transaction tool, an update or “patch” for a transaction tool, removalof a transaction tool, cancellation of a transaction tool, orreplacement of a transaction tool for the personal computercommunications devices 201, 202. The server 248 is provided with logicthat is used as a basis for the determinations related to theauthorizations for lifecycle events. The server 248 may also managelifecycle events for transaction tools installed on the personalcomputers 201, 202, even when the lifecycle events are not requested bythe user of the personal computers 201, 202. For example, the server 248may initiate cancellation of one or more digital certificates when theserver 248 determines that the digital certificates are compromised orissued by an untrustworthy issuer. Data for the lifecycle events andactivities of the transaction tools, including requested changes thatwere not ultimately authorized, is stored in the database 249.

As another example, the personal computer communications devices 201,202 may be used by a credit card recipient to perform transactions overthe internet. The change management/transaction tool management system240 receives requests for changes to the status of the credit cards. Forexample, a user of the personal computer 201 may request an increase inthe credit line for a credit card. The request is processed by thechange management/transaction tool management system 240, and theinformation of the request and authorization or denial is stored in thedatabase 249.

As an example of the uses of the communications network architectureshown in FIG. 2, a credit card company may allow credit card users toactivate or cancel a credit card, review transaction and paymenthistory, and conduct transactions such as cash advances or balancetransfers, by contacting the credit card company's servers over theinternet. The change management/transaction tool management system 240processes information for the credit card company's customers. However,the credit card company provides customers with the ability to conductboth normal inquiry and credit authorizations, as well as to requestlifecycle changes for the credit card. Accordingly, the changemanagement/transaction tool management system 240 stores and processesinformation related to changes in the status of credit cards issued tousers of the personal computers 201, 202. According to the embodimentshown in FIG. 2, an integrated change management/transaction toolmanagement system 240 can be used for processing activity and lifecycleevent information of credit cards issued to users of the personalcomputers 201, 202. As a result, human interaction in lifecycle eventprocessing is greatly reduced by using a system that integratestransaction tool management with change management.

FIG. 3 shows another exemplary communications network architecture fortransaction tool management integration with change management. In theembodiment shown in FIG. 3, personal computer communications device 301is connected to a switch 310 via a router 302. The router 302 translatespacketized data such as Voice over Internet Protocol samples intoaudible speech samples that are routed through a telecommunicationsnetwork that includes the switch 310. A telephone communications device304 is also connected to the switch 310 via a switch 305.

The switch 310 is connected to an intelligent peripheral communicationsplatform 322 that is a component of a transaction tool system 320. Thetransaction tool system 320 also includes a transaction tool server 328.The intelligent peripheral communications platform 322 interacts withusers of the personal computer 301 and/or the telephone 304 usingaudible signals and interacts with the transaction tool server 328 usingdata signals.

The transaction tool system 320 performs transactions for customers,clients or employees that are issued transaction tools, such as creditcards. For example, the transaction tool system 320 obtains informationof the transaction tool and ascertains whether the transaction tool isvalid and updated. Additionally, the transaction tool system 320 mayrequest additional information about the user of the personal computer301 or the telephone 304 to ensure the user is authorized to conducttransactions using the transaction tool.

A change management system 340 is provided separately from thetransaction tool system 320, and manages lifecycle changes fortransaction tools. The change management system 340 includes a server348 and a database 349. The server 348 communicates with the transactiontool server 328, and information for changes that are managed by thechange management system is stored in the database 349. For example, theuser of the personal computer 301 or the telephone 304 may report a lostcard or request a replacement of a lost credit card, in which case thechange management system 340 is contacted to obtain authorization forthe cancellation and/or replacement of the credit card. When lifecyclechanges for the credit card are made, the change management system 340informs the transaction tool system 320 so that transactions areproperly managed by the transaction tool system using the information ofthe change. As an example, the change management system 340 may informthe transaction tool system 320 to deny all transactions that areattempted using a lost or stolen credit card.

Accordingly, transaction tool management is integrated with changemanagement by providing the transaction tool system 320 and the changemanagement system 340 to users using the internet or atelecommunications system.

FIG. 4 shows an exemplary change management apparatus 400 fortransaction tool management integration with change management. Thechange management apparatus 400 includes a receiver 405 that receivesincoming requests from a transaction tool management system. A processor410 is also provided to centrally process transactions for the changemanagement apparatus 400, and a memory 420 is provided to storeinstructions and data for the change management apparatus 400. Theprocessor 410 executes instructions for a notification process module450, a transaction tool classification process module 452 and a changemanagement module 454.

The notification process module 450 includes instructions to notify auser, a manager, or a device when a change is authorized by the changemanagement apparatus 400 for a transaction tool. For example, a changethat is authorized for a digital certificate on a server may requireonly a notification to the manager responsible for the server and one ormore system managers. However, a change that requires shutting down andrebooting a system component may require approval of one or moremanagers. The notification process module 450 determines who to notifydepending on the transaction tool, the requested change, and theimplications, if any, that the change will have on system availability.

The transaction tool classification process module 452 classifiestransaction tools for the change management apparatus 400. For example,the transaction tool classification process module 452 may classifytransaction tools by the type and function of the computers on whichthey are installed. For example, for a large telecommunications systemthat provides digital certificates for both servers and, e.g., personalcomputers, lifecycle changes may be approved depending on theclassification and importance of the server or personal computer.Additionally, the timing of lifecycle changes that effect systemavailability may be determined based on the classifications made by thetransaction tool classification process module 452. In this regard, aninstallation, renewal or replacement of a digital certificate for anunimportant personal computer may not require anything more than anotification to the user when the change is approved. However, such achange for a digital certificate for a server that is used by the publicor numerous employees may require notification and approval of one ormore managers, particularly if the server is to be taken out of service.The request for a lifecycle change is made either automatically by thetransaction tool management system or by a requestor.

Where overlapping critical functionality is provided by a limited numberof devices, the change management apparatus 400 may determine that onlyone such device may be taken out of service at any time for lifecyclechanges. The transaction tool classification process module 452categorizes computers in the local network according to thefunctionality they provide. Of course, computers may be placed inmultiple categories depending on the various functions and services theyprovide.

The change management module 454 includes rules for the changemanagement. The change management module 454 determines whether aparticular change requires approvals or only notifications.Additionally, the change management module 454 may include logic todetermine when a requested change is to be authorized. For example,requests to install a digital certificate from a particular issuer maybe automatically denied if the issuer is deemed untrustworthy orunrecognized. Additionally, the change management module 454 mayschedule particular changes, to ensure system availability for redundantparts that cannot all be taken out of service at the same time. Thescheduling by the change management module 454 takes into considerationthe classifications by the transaction tool classification processmodule 452. As an example, if multiple servers are provided as internetgateways by an internet service provider, the servers for a particulargeographic area should not all be taken out of service at the same time,even if the transaction tools (e.g., digital certificates) installed onthe servers all expire at the same time. Accordingly, the changemanagement module may schedule replacements or renewals for transactiontools before the transaction tools expire.

FIG. 5 shows an exemplary method of operation for a change managementsystem that is integrated with a transaction tool management system.After the process starts, the change management system determineswhether installation information has been received and stored at S505.If installation information has been received and stored (S505=Yes), anapproval determination is made at S506 and notification is made at S507.If installation information has not been received (S505=No) or after thenotification at S507, the change management system determines whetheractivation information has been received and stored at S510. Ifactivation information has been received and stored (S510=Yes), anapproval determination is made at S511 and notifications is made atS512.

If activation information has not been received and stored (S510=No) orafter the notification at S512, the change management system determineswhether activity information has been received and stored at S515. Ifactivity information has been received (S515=Yes), an approvaldetermination is made at S516 and notification is made at S517.

If activity information is not received (S515=No) or after notificationis made at S517, the change management system determines whether upgradeinformation has been received and stored at S520. If upgrade informationhas been received and stored (S520=Yes), an approval determination ismade at S521 and notification is made at S522.

If upgrade information is not received (S520=No) or after notificationis made at S522, the change management system determines whetherdeactivation information has been received and stored at S525. Ifdeactivation information has been received and stored (S525=Yes), adetermination is made whether to replace or renew the transaction toolat S526 and notification is made at S527. The process ends at S530 ifdeactivation information has not been received (S525=No) or afternotification has occurred at S527.

Accordingly, a variety of activities and/or lifecycle events can bemanaged using the process shown in FIG. 5 or a similar process. Ofcourse, the steps shown in FIG. 5 may be performed in a different order,or not be performed at all. Furthermore, additional lifecycle events maybe managed by the change management system that performs the operationsshown in FIG. 5. For example, although not shown, the notificationsgenerated at S507, S512, S517, S522 and S527 may be requests that haveto be approved by specified individuals. Accordingly, the operations ofa change management system may include waiting for specific approvalfrom one or more notified individuals before the change managementsystem approves a requested change.

Further, rather than waiting for requests for lifecycle changes from auser, a transaction tool management system may initiate inquiries toobtain information of transaction tools installed on a network. Theretrieved information may be provided to a change management system thatschedules, in advance, lifecycle events, without waiting for thelifecycle events to be specifically requested by an end user. Anexemplary digital certificate discovery and management system which caninitiate inquiries is disclosed in U.S. patent application Ser. No.10/879,217 to NOVACK et al., filed on Jun. 30, 2004 and entitled“Automatic Digital Certificate Discovery and Management”, the disclosureof which is incorporated by reference herein in its entirety.

Although the invention has been described with reference to severalexemplary embodiments, it is understood that the words that have beenused are words of description and illustration, rather than words oflimitation. Changes may be made within the purview of the appendedclaims, as presently stated and as amended, without departing from thescope and spirit of the invention in its aspects. Although the inventionhas been described with reference to particular means, materials andembodiments, the invention is not intended to be limited to theparticulars disclosed; rather the invention extends to all functionallyequivalent structures, methods, and uses such as are within the scope ofthe appended claims. For example, instead of communicating with Voiceover Internet Protocol (VoIP), the personal computer 301 in FIG. 3 maycommunicate using multiprotocol label switching (MPLS) or any otherstandard for packet-switched communications.

In accordance with various embodiments of the present invention, themethods described herein are intended for operation as software programsrunning on a computer processor. Dedicated hardware implementationsincluding, but not limited to, application specific integrated circuits,programmable logic arrays and other hardware devices can likewise beconstructed to implement the methods described herein. Furthermore,alternative software implementations including, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the methods described herein.

It should also be noted that the software implementations of the presentinvention as described herein are optionally stored on a tangiblestorage medium, such as: a magnetic medium such as a disk or tape; amagneto-optical or optical medium such as a disk; or a solid statemedium such as a memory card or other package that houses one or moreread-only (non-volatile) memories, random access memories, or otherre-writable (volatile) memories. A digital file attachment to email orother self-contained information archive or set of archives isconsidered a distribution medium equivalent to a tangible storagemedium. Accordingly, the invention is considered to include a tangiblestorage medium or distribution medium, as listed herein and includingart-recognized equivalents and successor media, in which the softwareimplementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the invention is not limited to such standards andprotocols. For example, each of the standards for digital certificateformat (e.g., X.509) and packet switched network transmission (e.g.,VOIP, MPLS) represent examples of the state of the art. Such standardsare periodically superseded by faster or more efficient equivalentshaving essentially the same functions. Accordingly, replacementstandards and protocols having the same functions are consideredequivalents.

1. A change management system integrated with a transaction toolmanagement system including a processor for scheduling a change instatus of at least one transaction tool of the transaction toolmanagement system, the system comprising: a receiver that receives arequest for approval of the change in the status of the at least onetransaction tool; a storage that stores the received request; atransaction tool classification process module that classifiestransaction tools; and a change management module that schedules thechange in the status when the request for approval is approved, thechange management module using classification information from thetransaction tool classification process module to schedule the change inthe status, wherein the change management system uses informationavailable from the transaction tool management system to manage thechange in the status of the at least one transaction tool managed by thetransaction tool management system.
 2. The change management system ofclaim 1, wherein the transaction tool classification process moduleclassifies the transaction tools by type of hardware on which thetransaction tools are installed.
 3. The change management system ofclaim 1, wherein the transaction tool classification process moduleclassifies the transaction tools by functionality of hardware on whichthe transaction tools are installed.
 4. The change management system ofclaim 1, wherein the change in the status of the at least onetransaction tool comprises revoking the at least one transaction tool.5. The change management system of claim 1, wherein the request forapproval is contingent on approval from an authorized entity.
 6. Thechange management system of claim 1, further comprising a notificationprocess module that notifies a user when a change in status isauthorized.
 7. The change management system of claim 1, furthercomprising a notification process module that notifies a device when achange in status is authorized.
 8. A method for scheduling a change instatus of at least one transaction tool of the transaction tool managedby a transaction tool management system integrated with a changemanagement system, the method comprising: receiving, over acommunications network, a request for approval of the change in thestatus of the at least one transaction tool; storing the receivedrequest; classifying transaction tools; scheduling the change in thestatus when the request for approval is approved, the change managementmodule using classification information from the transaction toolclassification process module to schedule the change in the status,wherein the change management system uses information available from thetransaction tool management system to manage the change in the status ofthe at least one transaction tool managed by the transaction toolmanagement system.
 9. The method for scheduling a change in status of atleast one transaction tool of claim 8, wherein the transaction toolclassification process module classifies the transaction tools by typeof hardware on which the transaction tools are installed.
 10. The methodfor scheduling a change in status of at least one transaction tool ofclaim 8, wherein the transaction tool classification process moduleclassifies the transaction tools by functionality of hardware on whichthe transaction tools are installed.
 11. The method for scheduling achange in status of at least one transaction tool of claim 8, whereinthe change in the status of the at least one transaction tool comprisesrevoking the at least one transaction tool.
 12. The method forscheduling a change in status of at least one transaction tool of claim8, wherein the request for approval is contingent on approval from anauthorized entity.
 13. The method for scheduling a change in status ofat least one transaction tool of claim 8, further comprising anotification process module that notifies a user when a change in statusis authorized.
 14. The method for scheduling a change in status of atleast one transaction tool of claim 8, further comprising a notificationprocess module that notifies a device when a change in status isauthorized.
 15. A non-transitory computer readable medium storing aprogram that schedules a change in status of at least one transactiontool of the transaction tool managed by a transaction tool managementsystem integrated with a change management system, the non-transitorycomputer readable medium comprising: a receiving code segment thatreceives a request for approval of the change in the status of the atleast one transaction tool; a storing code segment that stores therequest; a classifying code segment that classifies transaction tools; ascheduling code segment that schedules a change in the status when therequest for approval is approved, the change management module usingclassification information from the transaction tool classificationprocess module to schedule the change in the status, wherein the changemanagement system uses information available from the transaction toolmanagement system to manage the change in the status of the at least onetransaction tool managed by the transaction tool management system. 16.The method for scheduling a change in status of at least one transactiontool of claim 15, wherein the transaction tool classification processmodule classifies the transaction tools by type and functionality ofhardware on which the transaction tools are installed.
 17. The methodfor scheduling a change in status of at least one transaction tool ofclaim 15, wherein the change in the status of the at least onetransaction tool comprises revoking the at least one transaction tool.18. The method for scheduling a change in status of at least onetransaction tool of claim 15, wherein the request for approval iscontingent on approval from an authorized entity.
 19. The method forscheduling a change in status of at least one transaction tool of claim15, further comprising a notification process module that notifies auser when a change in status is authorized.
 20. The method forscheduling a change in status of at least one transaction tool of claim15, further comprising a notification process module that notifies adevice when a change is in status authorized.